What changed

Wrapped extension-scoped one-shot setTimeout and requestAnimationFrame callbacks so fired handles remove themselves from the lifecycle registry and clearer maps. Extended the lifecycle sandbox harness with a flushable fake clock, explicit clear/cancel coverage, thrown-callback coverage, unmount cleanup coverage, and interval-retention assertions.

Why

Long-lived menu-bar extensions can schedule repeated one-shot timers over hours. Those fired handles no longer need lifecycle cleanup, but they previously stayed in registry.timeouts and registry.rafs, growing memory and future cleanup work until unmount or re-evaluation.

Compatibility impact

No extension API shape changes. Timeout callback arguments and practical browser this binding are preserved through the wrapper, explicit clearTimeout and cancelAnimationFrame still untrack and cancel pending handles, setImmediate continues to delegate through timeout cleanup, and unmount cleanup still clears pending one-shots. Interval behavior remains explicit-clear/unmount based and intervals stay tracked until cleared.

How tested

• node --test scripts/test-extension-lifecycle-sandbox.mjs -> 8/8 passing
• node --test 'scripts/test-*.mjs' -> 242/242 passing
• Codex LSP diagnostics with severity: error on src/renderer/src/ExtensionView.tsx -> no diagnostics

Performance evidence

• 1000 fired timeouts: before stale registry entries=1000, after=0
• 1000 fired RAFs: before stale registry entries=1000, after=0
• The same harness confirms intervals remain tracked after one-shot timeout/RAF callbacks fire, then drop to zero after explicit clear.

Stack validation

Implementation branch was created from fork/codex/perf-consolidated-integration-stack after verifying both HEAD and that stack branch resolved to integration base 264fb89dc5c867d6c3d77bc4b95e26e235e326ea.

Replaces

None